Construct

Construct details. (MORE INFO)

Construct: Hardware Quality



Note 1: Following are presented the definitions found for the construct in the used references, together with the theory/model.
Note 2: The same construct can be present in more than one theory/model.
Note 3: If the construct was not proposed in the original theory/model, it is identified as "Additional to theory/model".



Definition: Not defined.

Theory/model: Additional to DeLone and McLean
Reference: (Bradley, Pridmore, & Byrd, 2006)



Note 1: This list contains all the indicators (measuring variables) as defined by the authors when proposing/using/applying a theory/model in a context. It also includes the scales used to measure the variables.
Note 2: Some of the indicators are context-dependent.
Note 3: The same construct can be present in more than one theory/model.



IndicatorScaleContextTheory/ModelReference(s)
Hardware and operating systems are available for use 24 hours per day, seven days a week.Likert 1-7, Strongly Disagree to AgreeNot SpecifiedDM(Bradley, Pridmore, & Byrd, 2006)

Hardware and operating systems response times are adequate to keep users satisfied.Likert 1-7, Strongly Disagree to AgreeNot SpecifiedDM(Bradley, Pridmore, & Byrd, 2006)

Hardware and operating systems exhibit high degrees of reliability.Likert 1-7, Strongly Disagree to AgreeNot SpecifiedDM(Bradley, Pridmore, & Byrd, 2006)

Hardware and operating systems uptime are comparable to available user time.Likert 1-7, Strongly Disagree to AgreeNot SpecifiedDM(Bradley, Pridmore, & Byrd, 2006)